-
Notifications
You must be signed in to change notification settings - Fork 26
Default to Kubernetes 1.24 #859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🤖 Created branch: z_pr859/skitt/default-k8s-1.24 |
The upgrade job won’t work until we release 0.13.0 or 0.12.2. (0.12.1 doesn’t support Kubernetes 1.24.) |
The Helm jobs will fail because of submariner-io/submariner-charts#236. |
🤖 The base of this PR has been updated to devel |
... following review comments on submariner-io#859 Signed-off-by: Stephen Kitt <[email protected]>
@mkolesnik I’ve addressed your review comments in #864 (the code you were reviewing was already merged). |
... following review comments on submariner-io#859 * Drop the stutter in "kind_kind_binaries" * Remove the 1.14 shas, they'll change anyway * Default to kind and remove the explicit declarations for 1.17-1.23 * Don't log the kind binary explicitly, it's visible in the logs * Quote "${kind}" Signed-off-by: Stephen Kitt <[email protected]>
The Helm jobs are now fixed. @mkolesnik this is blocked by your request for changes, which doesn’t apply to this PR. |
... following review comments on #859 * Drop the stutter in "kind_kind_binaries" * Remove the 1.14 shas, they'll change anyway * Default to kind and remove the explicit declarations for 1.17-1.23 * Don't log the kind binary explicitly, it's visible in the logs * Quote "${kind}" Signed-off-by: Stephen Kitt <[email protected]>
I think we want to hold off on this until the lighthouse E2E resource issue 0.24 is resolved. |
Could you add that as a “request for changes” so it blocks the merge? Thanks! (I can’t do it since this is my own PR.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's hold this until the lighthouse issues are fixed.
I added it as "depends on", isn't that the preferred way of doing it? :) FWIW on LH this change won't affect the CI, but obviously when deployed manually one could potentially hit some issues, so I guess it makes sense to wait on LH CI to pass to be sure. We can also see jobs failing "E2E Consuming", including admiral which I think merits an investigation. |
I was thinking of the latter, and since they aren’t “Required” (the Lighthouse ones are failing, as well as Admiral), I wanted to avoid an accidental merge before they were fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting changes until the not-required Consuming Projects / E2E Consuming (admiral, operator, libreswan, 1.24)
job is passing.
Signed-off-by: Stephen Kitt <[email protected]>
It's passing now. |
This PR/issue depends on: |
@dfarrell07 could you update your review? |
🤖 Closed branches: [z_pr859/skitt/default-k8s-1.24] |
Signed-off-by: Stephen Kitt [email protected]
Depends on submariner-io/lighthouse#791
Depends on submariner-io/admiral#388